Delivery of third party content on a first party portal

ABSTRACT

The systems and methods are directed towards delivery of third party content onto a user device having a first party portal. The first party portal service facilitates the user viewing of third party content on the user device. In particular, the first party portal service retrieves third party content (e.g., video content streams) from third party content providers and provides the third party content in a format (i.e. channels) that allows users to easily view different types of content. Furthermore, the first party portal service facilitates the user in viewing the third party content alongside other existing channels available to cable television and streaming media/video on demand content.

BACKGROUND Field of Invention

The present invention generally relates to delivery of third partycontent to a user device. More specifically, the present inventionrelates to delivery of third party content on a first party portal.

Description of the Related Art

Cable television delivers television programming to paying subscribers.The television programming is provided to the subscribers from one ofmany existing providers (e.g., DirecTV, Verizon, AT&T U-verse). Bypaying a subscription, subscribers are provided access (from a provider)to “cable channels” such as HBO, MTV, Cartoon Network. In some cases,users could buy one or more channels as desired. In other cases, userswould need to purchase two or more channels at one time via a bundle.

In addition to cable television, there also exist services that allowusers to view streaming media and video on demand content on variouscomputing devices (e.g., mobile device, laptop, desktop). These services(e.g., Netflix, Hulu, Amazon Fire TV) may allow users to not only viewtelevision programming (similar to what is offered via cable television)but may include additional content such as movies and original onlinecontent.

Presently, there is another category of content (i.e. video content)that is currently not incorporated in either cable television orstreaming media/video on demand services. This category includes variousdifferent types of video content generated and streamed by individuals(referred also as third party content). For example, an example thirdparty content provider is Twitch.tv which allows users (i.e.broadcasters, streamers) to generate and provide streaming video contentto a live audience using the third party content provider website. Withthe example of Twitch, the broadcasters stream video content primarilyfocusing on video games.

The video content available on Twitch can be categorized into manydifferent channels. For example, the content can be categorized intovarious channels based on type of content (e.g., particular game or gametitle) or broadcaster/streamer. The content includes both the streamingvideo content as well as recordings of the streaming video content.

This category of live streaming video content has gained tremendouspopularity over the recent years. For example, Twitch.tv was reportedhas having 45 million unique viewers back in October 2013. Furthermore,in February 2014, Twitch.tv was reported as being the fourth largestsource of peak internet traffic. In 2015, Twitch announced that it hasover 1.5 million broadcasters (users streaming video content using thesite) and 100 million visitors per month.

With the existing services associated with cable television andstreaming media/video on demand, various functionalities have beenimplemented that facilitate user ease in viewing the content. Forexample, users are provided the ability to switch between differentcontent (i.e. channels) thereby browsing numerous channels without theneed to open or use alternative programs or applications. Users are alsoable to save (i.e. favorite) one or more channels that are frequentlyviewed.

No such functionality is currently available with respect to the thirdparty content. Users would need to navigate, for example, throughbrowser interfaces or opening new applications/programs in order tosearch for different individual streams to view. The searching viaexisting methods, when taking into account the numerous different gametitles and broadcasters available, is not only time consuming but wouldalso prevent users from easily viewing the full scope of what'savailable via the third party content provider (i.e. Twitch). There is aneed to provide similar functionality (i.e. channels) for the viewing ofthird party content that is already implemented with cable televisionand streaming media/video on demand so that the viewing audience couldmore efficiently and effectively view what is available.

SUMMARY OF THE CLAIMED INVENTION

A method for integrating third party content streams for viewing on auser device is presently claimed. The method covers the features wherebythird party content is provided to the user on the user device in achannel format, similar to how existing content is provided via cable,streaming media or video on demand services. The method includes arequest to view third-party content streams on a user device having afirst party portal. The request is used to identify the source of therequested third party content streams, via assistance of the first partyportal service. The user device and the third party content providerestablish a communication channel that facilitates the delivery ofinformation related to the requested third party content stream to theuser device. The first party portal service then extracts metadata fromthe delivered information which includes 1) descriptive information and2) format-based information. The descriptive information is mappedaccording to pre-determined categories of information that can bedisplayed alongside the video content stream on the user device. Theformat-based information dictates how the video content stream should beconverted in order to be compatible with the user device and/or firstparty portal service. Once the conversion is complete, the third partycontent stream and descriptive information is displayed on the userdevice for the user to view.

A system for integrating third party content streams for viewing on auser device is also presently claimed. The system includes one or morehost devices that host content (inclusive of third party contentstreams) that may be viewable by a user on their respective user devices(i.e. client devices). The system also includes a server associated witha first party portal service that provides information (i.e.instructions) used to establish communication between the client deviceand the host devices. Lastly, the system includes the client devicesfrom which the users are requesting to view third party content streams.These client devices are compatible with the first party portal serviceand perform various steps to retrieve the content from the host deviceand display that content for the user to view on the client device. Theclient device first receives a request to view third-party contentstreams. The request is used to identify the source of the requestedthird party content streams, via assistance of the first party portalservice. The client device and the host device establish a communicationchannel that facilitates the delivery of information related to therequested third party content stream to the client device. The firstparty portal service then extracts metadata from the deliveredinformation which includes 1) descriptive information and 2)format-based information. The descriptive information is mappedaccording to pre-determined categories of information that can bedisplayed alongside the video content stream on the client device. Theformat-based information dictates how the video content stream should beconverted in order to be compatible with the client device and/or firstparty portal service. Once the conversion is complete, the third partycontent stream and descriptive information is displayed on the clientdevice for the user to view.

A non-transitory computer-readable storage medium that includes aprogram that is executable by a processor to perform a method forintegrating third party content streams for viewing on a user device isalso presently claimed. The method executed by the processor covers thefeatures whereby third party content is provided to the user on the userdevice in a channel format, similar to how existing content is providedvia cable, streaming media or video on demand services. The methodincludes a request to view third-party content streams on a user devicehaving a first party portal service. The request is used to identify thesource of the requested third party content streams, via assistance ofthe first party portal service. The user device and the third partycontent provider establish a communication channel that facilitates thedelivery of information related to the requested third party contentstream to the user device. The first party portal service then extractsmetadata from the delivered information which includes 1) descriptiveinformation and 2) format-based information. The descriptive informationis mapped according to pre-determined categories of information that canbe displayed alongside the video content stream on the user device. Theformat-based information dictates how the video content stream should beconverted in order to be compatible with the user device and/or firstparty portal. Once the conversion is complete, the third party contentstream and descriptive information is displayed on the user device forthe user to view.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A and FIG. 1B illustrate exemplary systems for implementing thedelivery of third party content to a user device associated with a firstparty portal service.

FIG. 2 is an exemplary user device associated with the first partyportal service.

FIG. 3 is an exemplary first party portal service.

FIG. 4 illustrates an exemplary method of the first party portalservice.

DETAILED DESCRIPTION

The present disclosure describes how third party content can bedelivered to a user device having a first party portal. The first partyportal service facilitates the user viewing of third party content onthe user device. In particular, the first party portal service retrievesthird party content (e.g., video content streams) from third partycontent providers (e.g., Twitch) and provides them in a format (i.e.channels) that allows users to easily view different content on theiruser device. Furthermore, the first party portal service facilitates theuser in viewing the third party content alongside other existingchannels available to cable television and streaming media/video ondemand content. The first party portal service thereby provides the userthe option to utilize a single device for viewing a variety of differentcontent types without the need to utilize multiple applications,interfaces, or services.

In the past, “channels” referred to a band of frequencies used in radioand television transmission. These “channels” would be associated with aparticular station that provides content. Some exemplary cable channelsinclude HBO, MTV and Cartoon Network. As used herein, a “channel” refersto a collection of programs (i.e. content that a user can view). Each ofthese channels may have one or more different programs (i.e. shows,movies) that a user can view.

With the characteristic of being a channel, users (such as with cabletelevision) are able to view (e.g., search, scan) numerous differentchannels quickly using the same interface/application. In other words,users would not need to open different applications or interfaces toview content coming from different sources. Furthermore, users arecapable of performing various other functionalities that facilitate theviewing of a variety of different content without the need to utilizemultiple applications, interfaces or services (e.g., picture-in-picture,flashback, bookmarking).

FIG. 1A and FIG. 1B illustrate exemplary systems 100 for implementingthe delivery of third party content to a user device associated with afirst party portal service 110. In both the figures, the system 100includes the user device (i.e. client device) 110 associated with thefirst party portal service, a server 120 that carries out thefunctionalities of the first party portal service, and at least onethird-party content provider 130. In other embodiments, there maynumerous different user devices, servers and third-party contentproviders present.

As used herein, the first party portal refers to an application thatfacilitates 1) the retrieval and 2) display of content (e.g., streamingmedia) on the user device. The first party portal service instructionsmay be stored and executed on the user device 110. The functionalitiesassociated with the first party portal service may be pre-installed onthe user device 110 or provided by the server 120 as needed.

The server 120 provides a variety of different types ofinstructions/software or applications that carry out the processesinvolved with retrieving and displaying content on the user device. Forexample, the server 120 may include instructions for the user deviceassociated with the first party portal service that dictates 1) wherethe user device should go in order to obtain a particular type ofcontent (i.e. third party content), 2) how the user device can retrievethe content from a content provider, 3) how to format the retrievedcontent for compatibility with the first party portal service and theuser device, and 4) how to display the content on the user device.

The user device 110 (i.e. client device) can refer to any number ofdifferent computing devices. For example, the user device 110 may be agaming console, mobile device, laptop, or desktop. These exemplary userdevices 110 may have many different characteristics such as usingdifferent operating systems (e.g., iOS, Android), applications orcomputing languages (e.g., C++, JavaScript). Details regarding exemplaryuser devices 110 are provided below with reference to FIG. 2. It shouldbe noted that the first party portal service may include differentinstructions for different computing devices based on the differentcharacteristics.

The server 120 corresponds to one or more computing devices thatfacilitate operation of the first party portal service associated withthe user device 110. The server 120 may operate as a cloud-basedcomputing model that uses a network of different computing deviceshosted on the Internet to store, manage and process the data for thefirst party portal. The server 120 may communicate with the user device110 (via the Internet) on a regular basis in order to provide thenecessary instructions and applications used by the first party portalto carry out its various functionalities. Further details regarding theserver 120 are provided below with respect to FIG. 3.

The third-party content provider 130 includes any number of differentsources (i.e. hosts) of third party content available on the Internet.As described above, example third party content includes video contentstreams generated by individuals (i.e. broadcasters, streamers) that maybe viewed by any number of different viewers simultaneously. These videocontent streams may be hosted using a particular website associated withthe third party content provider (e.g., Youtube, Twitch, and Vine).

The system 100 may also access existing streaming media and/or video ondemand as well (not shown). The existing streaming media and/or video ondemand may be associated with their respective content providers (e.g.,HBO, Cartoon Network, MTV).

The exemplary system 100 as illustrated in FIG. 1A and FIG. 1B describetwo different possible modes of operation. In a first embodiment (asillustrated in FIG. 1A), the user device 110 may initially communicatewith the server 120 to obtain information about third party videocontent that the user would like to view. The information may includewhere (i.e. host website) the third party video content is hosted. Onceinformation is obtained, the user device 110 may subsequently initiatecommunications directly with the third party content provider 130 inorder to obtain the third party video content. Further details regardingthis embodiment are provided below (see FIG. 4).

In an alternative embodiment (as illustrated in FIG. 1B), the userdevice 110 can still initially communicate with the server 120 regardingthird party video content that the user would like to view. However,instead of the server 120 providing the information about where thethird party video content is hosted, the server 120 can instead reachout directly to the third party content provider 130. More specifically,the server 120 can instruct the third party content provider 130 toinitiate communications with the user device 110 in connection with theuser request to view third party video content hosted by the third partycontent provider 130.

In situations where there are numerous user devices 110 allcommunicating with the server 120 simultaneously, the embodimentillustrated in FIG. 1A may be chosen. Since each of the user devices 110initiate communications with the third party content providers 130separately, this avoids overloading the server 120 with too manyrequests from numerous different user devices 110 as the server 120 maynot be capable of initiating all the communications requests from thevarious user devices 110.

In an alternate situation, the embodiment illustrated in FIG. 1B may bechosen where fewer user devices 110 are simultaneously communicatingwith the server 120 regarding third party video content. By having theserver 120 initiate connections between the user device 110 and thethird party content provider 130, the amount of network traffic can bereduced as less communications are needed to establish connectionbetween the user device 110 and the third party content provider 130. Inthis way, this embodiment may facilitate the retrieval of third partyvideo content to the user device 110 from the third party contentprovider 130 more quickly than compared to the embodiment illustrated inFIG. 1A.

As described above, each of the embodiments for the system 100illustrated in FIG. 1A and FIG. 1B may have their respective benefitsfor operating in a particular manner based on the situation. As such,there may be systems where the two different embodiments are alsointerchangeable based on, for example, the number of requests beingprovided to the server during a given time period.

FIG. 2 is an exemplary user device associated with the first partyportal service 200. The exemplary user device 200 (e.g., desktop,laptop, tablet, mobile device, console gaming system) is a computingdevice that the user can utilize to facilitate carrying out features ofthe present invention pertaining to the viewing of third party content.

The user device associated with the first party portal service 200 mayinclude various elements as illustrated in FIG. 2. It should be notedthat the elements are exemplary and that other embodiments mayincorporate more or less than the elements illustrated. With referenceto FIG. 2, the user device associated with the first party portalservice 200 includes a main memory 202, a central processing unit (CPU)204, at least one vector unit 206, a graphics processing unit 208, aninput/output (I/O) processor 210, an I/O processor memory 212, acontroller interface 214, a memory card 216, a Universal Serial Bus(USB) interface 218, and an IEEE 1394 interface 220, an auxiliary (AUX)interface 222 for connecting a tracking device 224, although other busstandards and interfaces may be utilized. The user device associatedwith the first party portal service 200 further includes an operatingsystem read-only memory (OS ROM) 226, a sound processing unit 228, anoptical disc control unit 230, and a hard disc drive 232, which areconnected via a bus 234 to the I/O processor 210. The user deviceassociated with the first party portal service 200 further includes atleast one tracking device 224.

The tracking device 224 may be a camera, which includes eye-trackingcapabilities. The camera may be integrated into or attached as aperipheral device to user device associated with the first party portalservice 200. In typical eye-tracking devices, infrared non-collimatedlight is reflected from the eye and sensed by a camera or opticalsensor. The information is then analyzed to extract eye rotation fromchanges in reflections. Camera-based trackers focus on one or both eyesand record their movement as the viewer looks at some type of stimulus.Camera-based eye trackers use the center of the pupil and light tocreate corneal reflections (CRs). The vector between the pupil centerand the CR can be used to compute the point of regard on surface or thegaze direction. A simple calibration procedure of the viewer is usuallyneeded before using the eye tracker.

Alternatively, more sensitive trackers use reflections from the front ofthe cornea and that back of the lens of the eye as features to trackover time. Even more sensitive trackers image features from inside theeye, including retinal blood vessels, and follow these features as theeye rotates.

Most eye tracking devices use a sampling rate of at least 30 Hz,although 50/60 Hz is most common. Some tracking devises run as high as1250 Hz, which is needed to capture detail of very rapid eye movement.

A range camera may instead be used with the present invention to capturegestures made by the user and is capable of facial recognition. A rangecamera is typically used to capture and interpret specific gestures,which allows a hands-free control of an entertainment system. Thistechnology may use an infrared projector, a camera, a depth sensor, anda microchip to track the movement of objects and individuals in threedimensions. This user device may also employ a variant of image-basedthree-dimensional reconstruction.

The tracking device 224 may include a microphone integrated into orattached as a peripheral device to the user device associated with thefirst party portal service 200 that captures voice data. The microphonemay conduct acoustic source localization and/or ambient noisesuppression.

Alternatively, tracking device 224 may be the controller of the userdevice associated with the first party portal service 200. Thecontroller may use a combination of built-in accelerometers and infrareddetection to sense its position in 3D space when pointed at the LEDs ina sensor nearby, attached to, or integrated into the console of theentertainment system. This design allows users to controlfunctionalities of the user device associated with the first partyportal service 200 with physical gestures as well as button-presses. Thecontroller connects to the user device associated with the first partyportal service 200 using wireless technology that allows data exchangeover short distances (e.g., 30 feet). The controller may additionallyinclude a “rumble” feature (i.e., a shaking of the controller duringcertain points in the game) and/or an internal speaker.

The controller may additionally or alternatively be designed to capturebiometric readings using sensors in the remote to record data including,for example, skin moisture, heart rhythm, and muscle movement.

As noted above, the user device associated with the first party portalservice 200 may be an electronic gaming console. Alternatively, the userdevice associated with the first party portal service 200 may beimplemented as a general-purpose computer, a set-top box, or a hand-heldgaming device. Further, similar user devices may contain more or lessoperating components.

The CPU 204, the vector unit 206, the graphics processing unit 208, andthe I/O processor 210 communicate via a system bus 236. Further, the CPU204 communicates with the main memory 202 via a dedicated bus 238, whilethe vector unit 206 and the graphics processing unit 208 may communicatethrough a dedicated bus 240. The CPU 204 executes programs stored in theOS ROM 226 and the main memory 202. The main memory 202 may containpre-stored programs and programs transferred through the I/O Processor210 from a CD-ROM, DVD-ROM, or other optical disc (not shown) using theoptical disc control unit 232. The I/O processor 210 primarily controlsdata exchanges between the various devices of the user device associatedwith the first party portal service 200 including the CPU 204, thevector unit 206, the graphics processing unit 208, and the controllerinterface 214.

The graphics processing unit 208 executes graphics instructions receivedfrom the CPU 204 and the vector unit 206 to produce images for displayon a display device (not shown). For example, the vector unit 206 maytransform objects from three-dimensional coordinates to two-dimensionalcoordinates, and send the two-dimensional coordinates to the graphicsprocessing unit 208. Furthermore, the sound processing unit 230 executesinstructions to produce sound signals that are outputted to an audiodevice such as speakers (not shown).

A user of the user device associated with the first party portal service200 provides instructions via the controller interface 214 to the CPU204. For example, the user may instruct the CPU 204 to store certaininformation on the memory card 216 or instruct the user device 200 toperform some specified action.

Other devices may be connected to the user device associated with thefirst party portal service 200 via the USB interface 218, the IEEE 1394interface 220, and the AUX interface 222. Specifically, a trackingdevice 224, including a camera or a sensor may be connected to the userdevice associated with the first party portal service 200 via the AUXinterface 222, while a controller may be connected via the USB interface218.

FIG. 3 is an exemplary first party portal service 300. The first partyportal service 300 includes a plurality of different elements thatcollectively work together in order to deliver content from a variety ofdifferent video content sources 310 for the user to view on the clientdevice (i.e. user device) 340.

The first party portal service 300 can obtain video content from avariety of different video content sources 310. For example, the firstparty portal service 300 can access existing streaming media and/orvideo on demand (e.g., movies, television shows, online shows) in asimilar manner as other existing services such as Netflix and Hulu.Furthermore, the first party portal service 300 can also access thirdparty video content from various third party content providers (e.g.,Twitch, Youtube, Vine). Such third party content presently is notaccessible via existing services such as Netflix and Hulu.

The Content Provider Server API (Application Program Interface) 320provides instructions usable by the client device 340 associated withthe first party platform service regarding how to access content (e.g.,streaming media, video on demand, third party content) from thedifferent video content sources 310. Additional information, such asmetadata, about the accessed content can also be provided by the ContentProvider Server API 320 to the client device 340. As described below,the additional information (i.e. metadata) can be usable to providedetails about the content being shown to the user on the client device340. Finally, additional services associated with the accessed contentsuch as chat services, ratings and profiles can also be provided fromthe video content sources 310 to the user device 340 via the ContentProvider Server API 320.

The Content Provider Server API 320 may be provided by each of the oneor more video content sources (i.e. third-party content provider) 310.The Content Provider Server API 320 facilitates access of each of theclient devices 340 to the content hosted by the third party contentproviders 310. This may mean that with each unique source of content310, there may be a unique Content Provider Server API 320 that wouldfacilitate the client device 340 in accessing the content hosted by thatcontent source 310. There may be embodiments where Content ProviderServer APIs 320 are shared between two or more sources of content 310where requirements for access of the content by the client device 150are similar.

The Content Provider Server API 320 is accessed by a backend servicelayer 330 in order to obtain information about available content for theclient device 340. As described below, the additional information aboutthe content may include metadata (e.g., author, title, genre) describingthe available content. The information may also include a location wherethe content is stored (e.g., URL) so that the user device can proceedwith retrieving the content from the content source 310. Furthermore,the Content Provider Server API 320 may include instructions forimplementing functionalities such as chat that would allow differentusers simultaneously viewing the same content to interact with eachother in real time. Such instructions are used by the backend servicelayer 330 to carry out the functionalities on the client device 340.

As illustrated in the figure, the first party portal service 300 alsoincludes a back end service 330 that carries out the first party portalservices for the client device 340. The backend service 330 isresponsible for communicating with the different content sources 310that have available content for the user to view and perform processesto have that content available to the user on the client device 340. Thebackend service 330 would carry out instructions, for example, thatwould facilitate identifying formats of the content and subsequentlyformatting the content from these different content sources 310 so thatthey are usable by the client device 340. This may include identifyingthe metadata associated with each of the content then using variousdifferent types of conversion techniques so that data stored in oneformat with respect to the content sources 310 can be rendered anddisplayed on the client devices 340, which may correspond to a secondformat.

As indicated above, the first party portal service 300 is compatiblewith any number of different client devices 340. This compatibility witheach different type of client device 340 can be implemented using thebackend services 330. The client device 340 (i.e. the user device) caninclude a plurality of different computing devices. For example, theclient device 340 may include any number of different gaming consoles,mobile devices, laptops, and desktops. These client devices 340 may alsorun using a variety of different operating systems (e.g., iOS, Android),applications or computing languages (e.g., C++, JavaScript). Detailsregarding exemplary client devices 340 have been provided above withrespect to FIG. 2.

FIG. 4 illustrates an exemplary method 400 for implementing the deliveryof third party content to the user device through the use of the firstparty portal service. In an embodiment, the exemplary method 400 wouldbe used to facilitate the user in viewing a particular video contentstream from the third party content provider on the user device. Itshould be noted that the exemplary method 400 could also be used tofacilitate the user viewing of any type of content (e.g., streamingmedia, video on demand) on the user device. In some embodiments, themethod 400 illustrated in the figure is implemented via the backendservice associated with the first party portal service (see FIG. 3).

In step 405, the user (via a user interface associated with the userdevice) can transmit a request from the user device to the serverrequesting to view streaming video content from a particular third partycontent provider. This request can be provided via the user interface(e.g., search engine, text box) associated with the first partyplatform. For example, the user may provide a type of third partycontent they would like to view using one or more descriptions (e.g.,type of content, author, title of stream).

In other embodiments, the user view request can instead be resolved atthe user device itself. For example, the server may have providedvarious instructions, applications or search-related information (e.g.,location-based information of the third party content providers) to theuser device at a previous time (e.g., during initiation of the userdevice) or may provide such information on a regular basis to the userdevice. Using the information from the server, the user device canprocess the user view request if the information is available on theuser device. If the information provided beforehand is not available,this may trigger the request to be transmitted to the server forprocessing.

Once the user viewing request is received, information regarding therequest is obtained. This information may include looking up where (i.e.location on the Internet) where the third party content providerassociated with the third party content is located. This information mayavailable in a database, stored on the server and/or the user device. Insituations where the user device does not have this information readilyavailable, this information is returned from the server to the userdevice to facilitate user device's retrieval of the third party contentfrom the third part content provider.

Once the location of the third party content provider is obtained, theuser device begins locating where the requested third party content(i.e. video content stream) in step 410. As noted above, the userviewing request can include descriptive information that can identifyone or more related video content streams that the user may wish toview. Such information may include the name of the video content stream,the subject matter (i.e. game or game title) of the video contentstreams that the user would like to view, or one or more authors (i.e.broadcaster/streamer) associated with a subject matter that the userwould like to view. This information can be provided from the userdevice to a particular video content provider via the back end service(see FIG. 3) in order to identify one or more streams that the user maywant to view related to the user request.

Once one or more related video content streams have been located, theuser device and the third party content provider can establish acommunication channel in step 415. The communication channel will allowthe user device to retrieve information (e.g., video content stream,metadata) from the third party content provider (i.e. website) that willsubsequently be displayed on the user device. This communication channelmay include a variety of security features (e.g., user accounts,password, encryption) to ensure that 1) legitimate user devices areaccessing the third party video content and 2) the information beingtransmitted between the user device and the third party content provideris not tampered with by outside parties.

In some embodiments, the user device may first establish a communicationchannel with a particular third party content provider prior toproviding the descriptive information from the viewing request used toidentify relevant third party video content (i.e. third party contentstream, video on demand) that the user would like to view. The thirdparty content provider can subsequently transmit the related third partycontent streams based on the descriptive information provided by theuser. The more descriptive the user request is, the more likely thethird party content provider can provide a particular third partycontent stream (if applicable).

Once one or more related third party content streams have beenidentified based on the user request, the third party content providercan transmit information to the user device related to the third partyvideo content streams. The user device (in step 420) can proceed withidentifying and extracting the metadata associated with the transmittedthird party video content streams via the use of the backend service.

Metadata is described as being data that provides information aboutother data (i.e. the video content stream). In this case, the metadatamay describe what the subject matter of the video content stream is, theauthor(s) of the video content stream, when the video content stream wascreated, how long the video content stream is, location where the videocontent stream is stored, and any standards used to format and displaythe video content stream.

Extraction of the metadata is significant because 1) the metadata can beused to format the video content stream from its original format (e.g.,stored on the server) into a format that is compatible with the userdevice and/or the first party portal. Furthermore, 2) the descriptivedetails (e.g., title, authors) included in the metadata can be displayedon the user device for the user to view alongside the video contentstream. The descriptive details can be used to inform the user what iscurrently being displayed on the user device. These details can help theuser determine if the video content stream being displayed is thecorrect one that the user would like to view.

Once the metadata has been extracted, information from the metadata isparsed by the user device in step in order to determine the significanceof the extracted metadata. As noted above, the metadata may includeinformation that is descriptive to the video content stream. Suchinformation can be displayed for the user to view on the user device toinform the user what stream is currently being viewed. Furthermore,other information from the metadata can be used to format the stream tobe compatible with the user device.

The descriptive information included in the metadata is then mapped instep 425. The first party portal may include multiple pre-establishedcategories of information that are displayed on the user devicealongside the video content stream. These pre-established categories areused to inform the user information about the stream being viewed. Suchinformation may include the subject matter of the stream, the author(s)of the stream and titles associated with the stream. The metadataassociated with the video content stream obtained from the third partycontent provider may categorize similar information (e.g., title,author, subject matter) differently. The mapping performed in step 425recognizes that the information may be labeled differently for eachthird party content provider but aims to ensure that the information isreferenced the same way on the user device via the first party portal.

The mapping used in step 425 may be generated, for example, by anadministrator. The administrator may identify how each third partycontent provider may label related information for a particular videocontent stream. For example, the author of the stream may be identifiedby other content providers as broadcaster, streamer or merely as a user.This information may be labeled and stored differently based on thecontent provider. Regardless of how the third party content provideridentifies, stores or labels this information about the video contentstream, the mapping performed in step 425 ensures the information aboutthe author is associated with the appropriate pre-established categoryof information used by the first party portal. In this way, thisdescriptive information is displayed on the user device for the user toview alongside the video content stream in a consistent manner.

In step 430, the first party portal formats the video content streamcoming from the third party content provider. Formatting is determinedbased on the extracted metadata coming associated with the video contentstream. If the video content stream is already in a format that iscompatible with the user device, then no formatting may be needed.However, if the format identified in the extracted metadata is distinctfrom a format that is compatible with the user device, one or moreaspects of the video content stream may need to be modified.

As known in the art, video content streams may have a particular videoformat. These video formats can dictate how the data is stored and/orhow the video content is executed or displayed on user devices. Theformatting, performed in step 430, may utilize known conversion softwareor techniques in order to facilitate the display of the video contentstream specific for the user device. For example, the video content maybe provided with a default resolution for a default display screen size.The video content can be modified in order to have a resolution andsizing that corresponds to the user device.

The first party portal service associated with the user device includesvarious instructions that are usable in facilitating the formatting ofthe video content stream from one format to the format specific to theuser device. These instructions may be stored in a database, forexample, on the user device or on the server associated with the firstportal service. In situations where no instructions are available toconvert an aspect of the video content stream, this may 1) trigger theserver and/or user device to search one or more sources (e.g., theInternet) for any applicable instructions on how to convert theinformation into a format that is compatible with the user device, 2)overlook the issue and proceed with displaying the video content ontothe user device (if able), or 3) providing notice to the user that oneor more aspects of the video content stream cannot be formatted into amanner that is compatible with the user device thereby preventing thevideo content stream from being viewed on the user device.

Once the third party video content is formatted, the user device (viathe first party portal) can proceed with displaying the content for theuser to view in step 435. The displayed third party video content wouldinclude not only the video content stream but also related metadataextracted (in step 420) and mapped (in step 425). Exemplary metadatathat could be displayed by default could include the author(s) of thevideo content stream and the title. More or less metadata may becustomized, for example, by the user or first party portable, to bedisplayed alongside the video content stream.

In the embodiment described above (in step 405-step 435), a relationshipbetween the user device, server and third party content provider isprovided (see, FIG. 1A). In particular, the user device communicateswith the server initially to obtain information about the third partycontent provider. Subsequently, the user device communicates with thethird party content provider (based on the information obtained from theserver) in order to retrieve the third party content video stream.

It is also possible that a different relationship between the userdevice, server and third party content provider is also implemented(see, FIG. 1B). In particular, the user device could still communicatewith the server regarding the third party content that the user would beinterested in viewing. However, instead of providing the information tothe user device regarding where the third party content can be found onthe Internet (e.g., step 410), the server can subsequently communicatewith the third party content provider on the user device's behalfregarding the user view request. The third party content provider, usingthe information from the server, can initiate communication (i.e.establish a communication channel) with the user device associated withthe user view request. The established communication is then used todeliver the requested third party content video stream to the userdevice for display on the user device.

To facilitate the illustration of how method 400 would implement thedelivery of third party content, an example situation is provided belowwhereby a user is requesting to view a particular video content streamon a particular third party content provider website (e.g., Twitch). Thevideo content stream will be delivered to the user device associatedwith the first party portal service that is provided support from aserver associated with the first party portal service. It should benoted that other third party content providers can also be applicablehere. For example, third party content from other existing (and future)third party content providers may also be implemented here. (e.g.,Youtube, Vine).

Twitch may provide a variety of different streaming video contentcategorized under different genres, game titles or authors. Each ofthese genres and categories can further become broken down by any numberof different characteristics such as particular subject matter of thevideo content, the author(s) of the video content, and popularity.Therefore, the amount of information that a user provides in a userrequest in step 405 can better identify the video content streamcoincides with the user request.

The user request may be inputted via a user interface associated withthe user device. The first party portal may include one or more entriesassociated with a search engine that would facilitate the search for theparticular video content subject to the user request.

Using the user request, the computing device communicates with theserver in order to identify that the video content stream that the userwishes to view is located on Twitch (via step 410). In one embodiment,the computing device can communicate with the server (associated withthe first party portal service on the user device) in order to identifythat the user request is associated with a stream from Twitch.tv. Inanother embodiment, such information may already be stored on the userdevice (provided at a previous time by the server). This informationalso includes where (i.e. web address on the Internet) that Twitch islocated so that communications between the user device and Twitch can beestablished in order to retrieve the video content stream that will bedisplayed on the user device.

Once Twitch is identified as the source of the video content stream thatthe user would like to view, the user device can attempt to establishcommunication with the third party content provider in step 415. Thecommunication channel established between the user device and Twitchwould allow the user device to retrieve the video content stream (andrelated information) from Twitch.

In step 420, metadata associated with the video content stream can beextracted from the information being provided from Twitch to the userdevice via the communication channel. The metadata, which includesdescriptive information about the video content stream as well asformat-based information, can be extracted.

In step 425, the descriptive information obtained from the metadata (instep 420) can be mapped to pre-determined category of information thatis displayed on the user device. These types of information may include,for example, the author(s) of the video content stream, the subjectmatter (i.e. game title) or the title of the stream. Such informationwill be displayed alongside the video content stream in order to informthe user what exactly the user is viewing on the user device.

In step 430, the user device uses the format-based information obtainedfrom the metadata (in step 420) in order to format the video contentstream to be compatible with the user device. The methods for formattingthe video content stream can already be stored on the user device andexecuted as necessary. In some other embodiments, the user device mayneed to 1) communicate with the server or 2) search the Internet for thenecessary methods (i.e. applications, software, instructions) used toformat (e.g., convert) the video content stream into a form that iscompatible with the user device.

Alongside the formatting of the video content stream so that the videocontent stream can be compatible with the user device, step 430 may alsoinclude formatting the video content stream so that the video contentstream is compatible with the first party portal. In particular, thevideo content stream is formatted to resemble a “channel” similar toexisting cable channels or video on demand content. With the formattingof the content as a channel, a variety of functionalities can beperformed on the video content stream on the user device. Furtherdetails regarding these functionalities are provided below.

In step 435, the user is able to view the video content stream on theuser device. The descriptive information extracted from the metadata mayalso be displayed. The amount of descriptive information, as well aswhat types of descriptive information, to be displayed alongside thevideo content stream can be customized by the user or based on the firstparty portal service.

Once the video content stream is provided on the user device forviewing, the first party portal service allows the user to perform avariety of different functionalities. For example, the first partyportal service facilitates the user in saving (i.e. bookmarking) thirdparty content streams. This feature of saving/bookmarking allows theuser to store references to specific third party content streams inmemory. The user is then able to recall these references as desired(e.g., flashback mode) without the need to search up the specific thirdparty content stream again through the user interface (see step405-410).

The first party portal service is also capable of retrieving a pluralityof different third party content streams based on user view request.Each of these streams may be assigned a different channel therebyallowing the user to view (i.e. scan) multiple streams quickly andeasily without the need to perform individual processes to select astream to download, load up the stream for view and close the stream ifthe particular stream is not the one the user would like to view. Thisfunctionality would resemble a user scanning television channels ontheir television or searching through different programs on theirstreaming media service (e.g., Netflix). Since the third party contentstreams are available to the user device, via the first party portalservice, the user is able to switch and view numerous different streams(each assigned to their own channel) more quickly and easily.

Furthermore, the first party portal service may include differentchannels that contain particular characteristics. These channels may beprovided by default and are available for viewing upon initiation of thefirst party portal service. In other words, the user device mayautomatically be retrieving the content and making it available on theuser device without a specific user request. For example, these channelsmay, for example, provide to the user the most popular stream at acurrent time from a particular content provider. These channels may alsobe more specific (based on user preference) with respect to a particularsubject matter (i.e. game) or specific author (i.e. streamer). Althoughthe availability of these channels may be constantly changing (i.e. themost popular stream may dynamically change over time), the streamsassociated with these channels may be fixed when the first party portalfirst initiates and updated whenever the user manually updates a requestfor these channels.

Other functionalities associated with the first party portal include thesynchronization functionalities that may be present at the third partycontent provider that are also presented at the user device. Forexample, the first party portal may implement a chat service thatparallels a chat functionality that the third party content providerincludes with various third party content streams. These chat servicesmay allow numerous viewers to simultaneously communicate with oneanother with the contents of the stream. Although the user, via the userdevice, is not directly interacting with the chat functionality on thethird party content provider, the first party portal is able tosynchronize the information on the chat interface on the user devicewith the chat service at the third party content provider. In this way,comments provided by other users on the third party content providerwill appear on the user device as if these comments were directlyprovided to the user on the user device. Similarly, comments provided bythe user on the user device will appear in the chat functionality on thethird party content provider as if these comments were provided by theuser directly to the third party content provider.

In fact, even after the transmission of the stream data to the userdevice, the user device and the third party content provider mayconstantly be in communication with each other to push informationbetween the two (i.e. the client device and the third party contentprovider). For example, the user device may provide information aboutuser views (e.g., viewing history, preferences) to the third partycontent provider. The third party content provider may push information(such as advertisements based on information related to user views) thatmay be displayed on the user device.

As described above, the implementation of the first party portal servicewith respect to the third party content, allows users the furtherability to view a variety of different content all from a singleinterface. Users would not need to utilize multiple differentapplications or interfaces (e.g., browsers) in order to obtain content(e.g., third party content) to be viewed on their user device. The useof the first party portal serve, as described herein, increasesefficiency and time savings associated with allowing the user to viewall different types of content from a single interface. This efficiencyand time savings is significant as the nature of digital content changesover time. In particular, the benefits of the invention will be seen asbeing significant because of the increasing amounts of available digitalcontent for users to view and also the increasing of delivery speed ofcontent.

The foregoing detailed description of the technology herein has beenpresented for purposes of illustration and description. It is notintended to be exhaustive or to limit the technology to the precise formdisclosed. Many modifications and variations are possible in light ofthe above teaching. The described embodiments were chosen in order tobest explain the principles of the technology and its practicalapplication to thereby enable others skilled in the art to best utilizethe technology in various embodiments and with various modifications asare suited to the particular use contemplated. It is intended that thescope of the technology be defined by the claim.

What is claimed:
 1. A method for integrating third party content streamsfor viewing on a user device, the method comprising: transmitting arequest to view a third-party content stream on a user device, whereinthe third-party stream is hosted by a third party, and the request istransmitted from the user device; receiving metadata from a serverregarding the requested third-party content stream, wherein the metadataprovides instructions for establishing a communication connectionbetween the user device and the third party; receiving an identificationof at least one third-party content stream for viewing on the userdevice, wherein the identification is based on user input obtained fromthe user device; retrieving the identified third-party content streamfrom the third-party; extracting metadata from the retrieved third-partycontent stream, wherein the metadata is provided in a first format;parsing the extracted metadata into a plurality of characterizationsthat corresponds to descriptive information about the third-partycontent stream; mapping the characterizations of the extracted metadatafrom the third-party content stream to characterizations of a formatnative to the user device; and displaying the third-party content streamand metadata on the user device for the user to view in accordance withthe mapping.
 2. The method of claim 1, wherein the descriptive dataincludes a third-party content stream title.
 3. The method of claim 1,wherein the descriptive data includes one or more authors of thethird-party content stream.
 4. The method of claim 1 further comprisingtransmitting information corresponding to number of viewers associatedwith the displayed third-party content stream from the user device tothe third-party.
 5. The method of claim 1 further comprisingincorporating advertisements with the displayed third-party contentstream.
 6. The method of claim 5, wherein the incorporatedadvertisements are obtained from the third party.
 7. The method of claim5, further comprising synchronizing chat-based information between theuser device and the third-party content stream from the third-party. 8.The method of claim 1, wherein the displayed formatted third-partycontent stream is assigned a channel and is selectable by the user froma plurality of other channels each having its own content.
 9. The methodof claim 1 further comprising the user saving displayed third-partycontent streams for future viewing, wherein the saved third-partycontent streams are stored in a database that can be recalled by theuser upon request.
 10. The method of claim 1 further comprisingreceiving a query from the user device regarding a specific third-partycontent stream.
 11. The method of claim 10, wherein the query includes arequest for the specific third-party content stream having the mostcurrent number of views.
 12. A system for integrating third partycontent streams for viewing on a user device, the system comprising: oneor more host devices, wherein the host devices host content thatincludes third party content streams; a server associated with a firstparty portal service, wherein the server includes instructionsexecutable by a processor to: receive transmitted requests to view thirdparty content stream from the client device, and transmits metadata tothe client device that includes instructions for establishing thecommunication connection between the client device and the one or morecontent providers; and a client device that is compatible with the firstparty portal service, wherein the client device includes instructionsexecutable by a processor to transmit a request to view a third-partycontent stream on the client device to the server, receive metadata fromthe server regarding the requested third-party content stream, whereinthe metadata provides instructions for establishing a communicationconnection between the user device and the one or more host devices,receive an identification of at least one third-party content stream forviewing on the user device, wherein the identification is based on theuser request; retrieve the identified third-party content stream fromthe third-party; extract metadata from the retrieved third-party contentstream, wherein the metadata is provided in a first format; parse theextracted metadata into a plurality of characterizations thatcorresponds to descriptive information about the third-party contentstream; map the characterizations of the extracted metadata from thethird-party content stream to characterizations of a format native tothe client device; and display the third-party content stream andmetadata on the client for the user to view in accordance with themapping.
 13. The system of claim 12, wherein the descriptive dataincludes a third-party content stream title or authors of the thirdparty content stream.
 14. The system of claim 12, wherein the clientdevice further transmits information corresponding to number of viewersassociated with the displayed third-party content stream from the clientdevice to the host device.
 15. The system of claim 12, wherein theclient device further incorporates advertisements with the displayedthird-party content stream.
 16. The system of claim 15, wherein theincorporated advertisements are obtained from the host device.
 17. Thesystem of claim 15, wherein the client device further synchronizeschat-based information between the client device and the host device.18. The system of claim 15, wherein the displayed formatted third-partycontent stream is assigned a channel and is selectable by the user froma plurality of other channels each having its own content.
 19. Thesystem of claim 12, wherein the client device further allows the user tosave displayed third-party content streams for future viewing, whereinthe saved third-party content streams are stored in a database that canbe recalled by the user upon request.
 20. A non-transitorycomputer-readable storage medium, having embodied thereon a programexecutable by a processor to perform a method for integrating thirdparty content streams for viewing on a user device, the methodcomprising: transmitting a request to view a third-party content streamon a user device, wherein the third-party stream is hosted by a thirdparty, and the request is transmitted from the user device; receivingmetadata from a server regarding the requested third-party contentstream, wherein the metadata provides instructions for establishing acommunication connection between the user device and the third party;receiving an identification of at least one third-party content streamfor viewing on the user device, wherein the identification is based onuser input obtained from the user device; receiving the identifiedthird-party content stream from the third-party; extracting metadatafrom the received third-party content stream, wherein the metadata isprovided in a first format; parsing the extracted metadata into aplurality of characterizations that corresponds to descriptiveinformation about the third-party content stream; mapping thecharacterizations of the extracted metadata from the third-party contentstream to characterizations of a format native to the user device; anddisplaying the third-party content stream and metadata on the userdevice for the user to view in according with the mapping.